ZAP Scanning Report

Generated on Mon, 14 Mar 2022 03:25:20

Summary of Alerts

Risk Level Number of Alerts
High
2
Medium
11
Low
5
Informational
6
False Positives:
0

Alerts

Name Risk Level Number of Instances
Anti-CSRF Tokens Check High 4
Proxy Disclosure High 19
Absence of Anti-CSRF Tokens Medium 4
Backup File Disclosure Medium 2
CORS Misconfiguration Medium 19
Content Security Policy (CSP) Header Not Set Medium 6
Cross-Domain Misconfiguration Medium 15
Hidden File Found Medium 1
Insecure HTTP Method - PATCH Medium 1
Insecure HTTP Method - PUT Medium 19
Missing Anti-clickjacking Header Medium 4
Vulnerable JS Library Medium 1
Web Cache Deception Medium 4
Dangerous JS Functions Low 1
In Page Banner Information Leak Low 2
Permissions Policy Header Not Set Low 9
Server Leaks Version Information via "Server" HTTP Response Header Field Low 15
X-Content-Type-Options Header Missing Low 13
Base64 Disclosure Informational 1
Information Disclosure - Suspicious Comments Informational 3
Modern Web Application Informational 5
Non-Storable Content Informational 4
Storable and Cacheable Content Informational 11
User Agent Fuzzer Informational 28

Passing Rules

Name Rule Type Threshold Strength
Directory Browsing Active MEDIUM MEDIUM
Path Traversal Active MEDIUM MEDIUM
Remote File Inclusion Active MEDIUM MEDIUM
XSLT Injection Active MEDIUM MEDIUM
Server Side Code Injection Active MEDIUM MEDIUM
Advanced SQL Injection Active MEDIUM MEDIUM
XPath Injection Active MEDIUM MEDIUM
Remote OS Command Injection Active MEDIUM MEDIUM
XML External Entity Attack Active MEDIUM MEDIUM
Expression Language Injection Active MEDIUM MEDIUM
Generic Padding Oracle Active MEDIUM MEDIUM
Source Code Disclosure - Git Active MEDIUM MEDIUM
Cookie Slack Detector Active MEDIUM MEDIUM
Source Code Disclosure - SVN Active MEDIUM MEDIUM
SOAP Action Spoofing Active MEDIUM MEDIUM
Source Code Disclosure - File Inclusion Active MEDIUM MEDIUM
SOAP XML Injection Active MEDIUM MEDIUM
HTTP Parameter Pollution Active MEDIUM MEDIUM
Heartbleed OpenSSL Vulnerability Active MEDIUM MEDIUM
Cross-Domain Misconfiguration Active MEDIUM MEDIUM
Source Code Disclosure - CVE-2012-1823 Active MEDIUM MEDIUM
Buffer Overflow Active MEDIUM MEDIUM
Remote Code Execution - CVE-2012-1823 Active MEDIUM MEDIUM
Format String Error Active MEDIUM MEDIUM
Integer Overflow Error Active MEDIUM MEDIUM
Cloud Metadata Potentially Exposed Active MEDIUM MEDIUM
External Redirect Active MEDIUM MEDIUM
Source Code Disclosure - /WEB-INF folder Active MEDIUM MEDIUM
HTTPS Content Available via HTTP Active MEDIUM MEDIUM
Remote Code Execution - Shell Shock Active MEDIUM MEDIUM
Relative Path Confusion Active MEDIUM MEDIUM
CRLF Injection Active MEDIUM MEDIUM
Example Active Scan Rule: Denial of Service Active MEDIUM MEDIUM
An example active scan rule which loads data from a file Active MEDIUM MEDIUM
Parameter Tampering Active MEDIUM MEDIUM
Server Side Include Active MEDIUM MEDIUM
GET for POST Active MEDIUM MEDIUM
Cross Site Scripting (Reflected) Active MEDIUM MEDIUM
Session Fixation Active MEDIUM MEDIUM
Cross Site Scripting (Persistent) Active MEDIUM MEDIUM
LDAP Injection Active MEDIUM MEDIUM
Script Active Scan Rules Active MEDIUM MEDIUM
Cross Site Scripting (Persistent) - Prime Active MEDIUM MEDIUM
Cross Site Scripting (Persistent) - Spider Active MEDIUM MEDIUM
SQL Injection Active MEDIUM MEDIUM
SQL Injection - MySQL Active MEDIUM MEDIUM
SQL Injection - Hypersonic SQL Active MEDIUM MEDIUM
SQL Injection - Oracle Active MEDIUM MEDIUM
SQL Injection - PostgreSQL Active MEDIUM MEDIUM
Possible Username Enumeration Active MEDIUM MEDIUM
SQL Injection - SQLite Active MEDIUM MEDIUM
Cross Site Scripting (DOM Based) Active MEDIUM MEDIUM
SQL Injection - MsSQL Active MEDIUM MEDIUM
ELMAH Information Leak Active MEDIUM MEDIUM
Trace.axd Information Leak Active MEDIUM MEDIUM
Out of Band XSS Active MEDIUM MEDIUM
.htaccess Information Leak Active MEDIUM MEDIUM
NoSQL Injection - MongoDB Active MEDIUM MEDIUM
.env Information Leak Active MEDIUM MEDIUM
JWT Scan Rule Active MEDIUM MEDIUM
Bypassing 403 Active MEDIUM MEDIUM
Active MEDIUM MEDIUM
Spring Actuator Information Leak Active MEDIUM MEDIUM
Log4Shell Active MEDIUM MEDIUM
Exponential Entity Expansion (Billion Laughs Attack) Active MEDIUM MEDIUM
HTTP Only Site Active MEDIUM MEDIUM
Httpoxy - Proxy Header Misuse Active MEDIUM MEDIUM
Private IP Disclosure Passive MEDIUM -
Session ID in URL Rewrite Passive MEDIUM -
Insecure JSF ViewState Passive MEDIUM -
Sub Resource Integrity Attribute Missing Passive MEDIUM -
Java Serialization Object Passive MEDIUM -
Insufficient Site Isolation Against Spectre Vulnerability Passive MEDIUM -
Charset Mismatch Passive MEDIUM -
Cookie No HttpOnly Flag Passive MEDIUM -
Cookie Without Secure Flag Passive MEDIUM -
Re-examine Cache-control Directives Passive MEDIUM -
Cross-Domain JavaScript Source File Inclusion Passive MEDIUM -
Content-Type Header Missing Passive MEDIUM -
Application Error Disclosure Passive MEDIUM -
Information Disclosure - Debug Error Messages Passive MEDIUM -
Information Disclosure - Sensitive Information in URL Passive MEDIUM -
Information Disclosure - Sensitive Information in HTTP Referrer Header Passive MEDIUM -
HTTP Parameter Override Passive MEDIUM -
Open Redirect Passive MEDIUM -
Cookie Poisoning Passive MEDIUM -
User Controllable Charset Passive MEDIUM -
User Controllable HTML Element Attribute (Potential XSS) Passive MEDIUM -
WSDL File Detection Passive MEDIUM -
Loosely Scoped Cookie Passive MEDIUM -
Viewstate Passive MEDIUM -
Directory Browsing Passive MEDIUM -
Heartbleed OpenSSL Vulnerability (Indicative) Passive MEDIUM -
Strict-Transport-Security Header Passive MEDIUM -
Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s) Passive MEDIUM -
X-Backend-Server Header Information Leak Passive MEDIUM -
Secure Pages Include Mixed Content Passive MEDIUM -
HTTP to HTTPS Insecure Transition in Form Post Passive MEDIUM -
HTTPS to HTTP Insecure Transition in Form Post Passive MEDIUM -
User Controllable JavaScript Event (XSS) Passive MEDIUM -
Big Redirect Detected (Potential Sensitive Information Leak) Passive MEDIUM -
Retrieved from Cache Passive MEDIUM -
X-ChromeLogger-Data (XCOLD) Header Information Leak Passive MEDIUM -
Cookie without SameSite Attribute Passive MEDIUM -
CSP Passive MEDIUM -
X-Debug-Token Information Leak Passive MEDIUM -
Username Hash Found Passive MEDIUM -
X-AspNet-Version Response Header Passive MEDIUM -
PII Disclosure Passive MEDIUM -
Script Passive Scan Rules Passive MEDIUM -
Stats Passive Scan Rule Passive MEDIUM -
Use of SAML Passive MEDIUM -
Example Passive Scan Rule: Denial of Service Passive MEDIUM -
An example passive scan rule which loads data from a file. Passive MEDIUM -
Timestamp Disclosure Passive MEDIUM -
Hash Disclosure Passive MEDIUM -
Source Code Disclosure Passive MEDIUM -
Image Location and Privacy Scanner Passive MEDIUM -
Weak Authentication Method Passive MEDIUM -
Reverse Tabnabbing Passive MEDIUM -

Sites

http://zero.webappsecurity.com

HTTP Response Code Number of Responses
501 Not Implemented
22
403 Forbidden
36
404 Not Found
766
405 Method Not Allowed
61
200 OK
751
400 Bad Request
6
302 Found
241

No Authentication Statistics Found

Technology Version Categories Implies
Apache Tomcat
Web servers
Java
Bootstrap
UI frameworks
Font Awesome
Font scripts
Java
Programming languages
jQuery
1.8.2
JavaScript libraries
Parameter Name Type Flags Times Used # Values

Alert Detail

High
Anti-CSRF Tokens Check
Description
A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.

CSRF attacks are effective in a number of situations, including:

* The victim has an active session on the target site.

* The victim is authenticated via HTTP auth on the target site.

* The victim is on the same local network as the target site.

CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
Instances 4
Solution
Phase: Architecture and Design

Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

For example, use anti-CSRF packages such as the OWASP CSRFGuard.

Phase: Implementation

Ensure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.

Phase: Architecture and Design

Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).

Note that this can be bypassed using XSS.

Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.

Note that this can be bypassed using XSS.

Use the ESAPI Session Management control.

This control includes a component for CSRF.

Do not use the GET method for any request that triggers a state change.

Phase: Implementation

Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
Reference http://projects.webappsec.org/Cross-Site-Request-Forgery
http://cwe.mitre.org/data/definitions/352.html
Tags OWASP_2021_A05
WSTG-v42-SESS-05
OWASP_2017_A06
CWE Id 352
WASC Id 9
Plugin Id 20012
High
Proxy Disclosure
Description
1 proxy server(s) were detected or fingerprinted. This information helps a potential attacker to determine

- A list of targets for an attack against the application.

- Potential vulnerabilities on the proxy servers that service the application.

- The presence or absence of any proxy-based components that might cause attacks against the application to be detected, prevented, or mitigated.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 264 bytes.
Request Body - size: 0 bytes.
Response Header - size: 186 bytes.
Response Body - size: 0 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 268 bytes.
Request Body - size: 0 bytes.
Response Header - size: 190 bytes.
Response Body - size: 0 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 285 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 268 bytes.
Request Body - size: 0 bytes.
Response Header - size: 190 bytes.
Response Body - size: 0 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 267 bytes.
Request Body - size: 0 bytes.
Response Header - size: 189 bytes.
Response Body - size: 0 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack TRACE, OPTIONS methods with 'Max-Forwards' header. TRACK method.
Evidence
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 19
Solution
Disable the 'TRACE' method on the proxy servers, as well as the origin web/application server.

Disable the 'OPTIONS' method on the proxy servers, as well as the origin web/application server, if it is not required for other purposes, such as 'CORS' (Cross Origin Resource Sharing).

Configure the web and application servers with custom error pages, to prevent 'fingerprintable' product-specific error pages being leaked to the user in the event of HTTP errors, such as 'TRACK' requests for non-existent pages.

Configure all proxies, application servers, and web servers to prevent disclosure of the technology and version information in the 'Server' and 'X-Powered-By' HTTP response headers.
Reference https://tools.ietf.org/html/rfc7231#section-5.1.2
Tags OWASP_2021_A05
OWASP_2017_A06
CWE Id 200
WASC Id 45
Plugin Id 40025
Medium
Absence of Anti-CSRF Tokens
Description
No Anti-CSRF tokens were found in a HTML submission form.

A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.

CSRF attacks are effective in a number of situations, including:

* The victim has an active session on the target site.

* The victim is authenticated via HTTP auth on the target site.

* The victim is on the same local network as the target site.

CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence <form action="/search.html" class="navbar-search pull-right" style="padding-right: 20px">
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
Instances 4
Solution
Phase: Architecture and Design

Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

For example, use anti-CSRF packages such as the OWASP CSRFGuard.

Phase: Implementation

Ensure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.

Phase: Architecture and Design

Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).

Note that this can be bypassed using XSS.

Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.

Note that this can be bypassed using XSS.

Use the ESAPI Session Management control.

This control includes a component for CSRF.

Do not use the GET method for any request that triggers a state change.

Phase: Implementation

Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
Reference http://projects.webappsec.org/Cross-Site-Request-Forgery
http://cwe.mitre.org/data/definitions/352.html
Tags OWASP_2021_A01
WSTG-v42-SESS-05
OWASP_2017_A05
CWE Id 352
WASC Id 9
Plugin Id 10202
Medium
Backup File Disclosure
Description
A backup of the file was disclosed by the web server
URL http://zero.webappsecurity.com/index.html.old
Method GET
Parameter
Attack http://zero.webappsecurity.com/index.html.old
Evidence A backup of [http://zero.webappsecurity.com/index.html] is available at [http://zero.webappsecurity.com/index.html.old]
Request Header - size: 247 bytes.
Request Body - size: 0 bytes.
Response Header - size: 289 bytes.
Response Body - size: 3,691 bytes.
URL http://zero.webappsecurity.com/index.old
Method GET
Parameter
Attack http://zero.webappsecurity.com/index.old
Evidence A backup of [http://zero.webappsecurity.com/index.html] is available at [http://zero.webappsecurity.com/index.old]
Request Header - size: 242 bytes.
Request Body - size: 0 bytes.
Response Header - size: 289 bytes.
Response Body - size: 3,691 bytes.
Instances 2
Solution
Do not edit files in-situ on the web server, and ensure that un-necessary files (including hidden files) are removed from the web server.
Reference https://cwe.mitre.org/data/definitions/530.html
https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/02-Configuration_and_Deployment_Management_Testing/04-Review_Old_Backup_and_Unreferenced_Files_for_Sensitive_Information.html
Tags OWASP_2021_A05
WSTG-v42-CONF-04
OWASP_2017_A03
CWE Id 530
WASC Id 34
Plugin Id 10095
Medium
CORS Misconfiguration
Description
This CORS misconfiguration could allow an attacker to perform AJAX queries to the vulnerable website from a malicious page loaded by the victim's user agent.

In order to perform authenticated AJAX queries, the server must specify the header "Access-Control-Allow-Credentials: true" and the "Access-Control-Allow-Origin" header must be set to null or the malicious page's domain. Even if this misconfiguration doesn't allow authenticated AJAX requests, unauthenticated sensitive content can still be accessed (e.g intranet websites).

A malicious page can belong to a malicious website but also a trusted website with flaws (e.g XSS, support of HTTP without TLS allowing code injection through MITM, etc).
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 261 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 262 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 313 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 312 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 316 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 334 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 333 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 325 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 316 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 336 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 336 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 336 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 315 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 332 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 335 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 335 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 272 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 329 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack Origin: http://4qCMHsQq.com
Evidence Access-Control-Allow-Origin: *
Request Header - size: 273 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 19
Solution
If a web resource contains sensitive information, the origin should be properly specified in the Access-Control-Allow-Origin header. Only trusted websites needing this resource should be specified in this header, with the most secured protocol supported.
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
https://portswigger.net/web-security/cors
Tags OWASP_2021_A01
WSTG-v42-CLNT-07
OWASP_2017_A05
CWE Id 942
WASC Id 14
Plugin Id 40040
Medium
Content Security Policy (CSP) Header Not Set
Description
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 6
Solution
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header, to achieve optimal browser support: "Content-Security-Policy" for Chrome 25+, Firefox 23+ and Safari 7+, "X-Content-Security-Policy" for Firefox 4.0+ and Internet Explorer 10+, and "X-WebKit-CSP" for Chrome 14+ and Safari 6+.
Reference https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
http://www.w3.org/TR/CSP/
http://w3c.github.io/webappsec/specs/content-security-policy/csp-specification.dev.html
http://www.html5rocks.com/en/tutorials/security/content-security-policy/
http://caniuse.com/#feat=contentsecuritypolicy
http://content-security-policy.com/
Tags OWASP_2021_A05
OWASP_2017_A06
CWE Id 693
WASC Id 15
Plugin Id 10038
Medium
Cross-Domain Misconfiguration
Description
Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 285 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence Access-Control-Allow-Origin: *
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 15
Solution
Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).

Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.
Reference https://vulncat.fortify.com/en/detail?id=desc.config.dotnet.html5_overly_permissive_cors_policy
Tags OWASP_2021_A01
OWASP_2017_A05
CWE Id 264
WASC Id 14
Plugin Id 10098
Medium
Hidden File Found
Description
A sensitive file was identified as accessible or available. This may leak administrative, configuration, or credential information which can be leveraged by a malicious individual to further attack the system or conduct social engineering efforts.
URL http://zero.webappsecurity.com/server-status
Method GET
Parameter
Attack
Evidence HTTP/1.1 200 OK
Request Header - size: 246 bytes.
Request Body - size: 0 bytes.
Response Header - size: 176 bytes.
Response Body - size: 5,523 bytes.
Instances 1
Solution
Consider whether or not the component is actually required in production, if it isn't then disable it. If it is then ensure access to it requires appropriate authentication and authorization, or limit exposure to internal systems or specific source IPs, etc.
Reference https://blog.hboeck.de/archives/892-Introducing-Snallygaster-a-Tool-to-Scan-for-Secrets-on-Web-Servers.html
https://httpd.apache.org/docs/current/mod/mod_status.html
Tags OWASP_2021_A05
WSTG-v42-CONF-05
OWASP_2017_A06
CWE Id 538
WASC Id 13
Plugin Id 40035
Medium
Insecure HTTP Method - PATCH
Description
This method is now most commonly used in REST services, PATCH is used for **modify** capabilities. The PATCH request only needs to contain the changes to the resource, not the complete resource.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP/nqmmqbc6ng
Method PATCH
Parameter
Attack
Evidence response code 200 for insecure HTTP METHOD
Request Header - size: 314 bytes.
Request Body - size: 35 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,734 bytes.
Instances 1
Solution
TBA
Reference http://projects.webappsec.org/Fingerprinting
Tags OWASP_2021_A05
WSTG-v42-CONF-06
OWASP_2017_A06
CWE Id 200
WASC Id 45
Plugin Id 90028
Medium
Insecure HTTP Method - PUT
Description
This method was originally intended for file managemant operations. It is now most commonly used in REST services, PUT is most-often utilized for **update** capabilities, PUT-ing to a known resource URI with the request body containing the newly-updated representation of the original resource..
URL http://zero.webappsecurity.com/8h1i8wnsf9
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 244 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/index.html/4xn4l45vhi
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 296 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css/8dtr4hk3dd
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 317 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css/90c6zmyiao
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 316 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/css/ide2zhpalh
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 299 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css/uerz8c15fz
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 308 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/img/c05fziuw3h
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 299 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg/hxw23j0tad
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 319 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg/i4v7bgrre1
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 319 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg/3nh3dzfmok
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 319 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js/w09zs5my4m
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 315 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js/h71neugl5l
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 318 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js/9ggir42lsl
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 318 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/js/w091v9w9qh
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 298 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/resources/xyb0qfzi18
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 295 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/robots.txt/lab09vgo1e
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 255 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP/5x2ara2vvo
Method PUT
Parameter
Attack
Evidence response code 200 for insecure HTTP METHOD
Request Header - size: 312 bytes.
Request Body - size: 35 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,734 bytes.
URL http://zero.webappsecurity.com/sitemap.xml/sq15qitqmv
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 256 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
URL http://zero.webappsecurity.com/w0zzu8fupw
Method PUT
Parameter
Attack
Evidence response code 403 for potentially insecure HTTP METHOD
Request Header - size: 244 bytes.
Request Body - size: 35 bytes.
Response Header - size: 204 bytes.
Response Body - size: 961 bytes.
Instances 19
Solution
TBA
Reference http://projects.webappsec.org/Fingerprinting
Tags OWASP_2021_A05
WSTG-v42-CONF-06
OWASP_2017_A06
CWE Id 200
WASC Id 45
Plugin Id 90028
Medium
Missing Anti-clickjacking Header
Description
The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.
URL http://zero.webappsecurity.com
Method GET
Parameter X-Frame-Options
Attack
Evidence
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter X-Frame-Options
Attack
Evidence
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter X-Frame-Options
Attack
Evidence
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter X-Frame-Options
Attack
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
Instances 4
Solution
Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.

If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
Tags OWASP_2021_A05
WSTG-v42-CLNT-09
OWASP_2017_A06
CWE Id 1021
WASC Id 15
Plugin Id 10020
Medium
Vulnerable JS Library
Description
The identified library jquery, version 1.8.2 is vulnerable.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence jquery-1.8.2.min.js
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
Instances 1
Solution
Please upgrade to the latest version of jquery.
Reference https://nvd.nist.gov/vuln/detail/CVE-2012-6708
https://github.com/jquery/jquery/issues/2432
http://research.insecurelabs.org/jquery/test/
http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
http://bugs.jquery.com/ticket/11290
https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/
https://nvd.nist.gov/vuln/detail/CVE-2019-11358
https://nvd.nist.gov/vuln/detail/CVE-2015-9251
https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b
https://bugs.jquery.com/ticket/11974
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
Tags OWASP_2017_A09
OWASP_2021_A06
CWE Id 829
WASC Id
Plugin Id 10003
Medium
Web Cache Deception
Description
Web cache deception may be possible. It may be possible for unauthorised user to view sensitive data on this page.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter
Attack /test.css,/test.jpg,/test.js,/test.html,/test.gif,/test.png,/test.svg,/test.php,/test.txt,/test.pdf,/test.asp,
Evidence
Request Header - size: 283 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter
Attack /test.css,/test.jpg,/test.js,/test.html,/test.gif,/test.png,/test.svg,/test.php,/test.txt,/test.pdf,/test.asp,
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter
Attack /test.css,/test.jpg,/test.js,/test.html,/test.gif,/test.png,/test.svg,/test.php,/test.txt,/test.pdf,/test.asp,
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter
Attack /test.css,/test.jpg,/test.js,/test.html,/test.gif,/test.png,/test.svg,/test.php,/test.txt,/test.pdf,/test.asp,
Evidence
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
Instances 4
Solution
It is strongly advised to refrain from classifying file types, such as images or stylesheets solely by their URL and file extension. Instead you should make sure that files are cached based on their Content-Type header.
Reference https://blogs.akamai.com/2017/03/on-web-cache-deception-attacks.html
https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/web-cache-deception/
Tags OWASP_2021_A05
WSTG-v42-ATHN-06
OWASP_2017_A06
CWE Id
WASC Id
Plugin Id 40039
Low
Dangerous JS Functions
Description
A dangerous JS function seems to be in use that would leave the site vulnerable.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence eval
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
Instances 1
Solution
See the references for security advice on the use of these functions.
Reference https://angular.io/guide/security
Tags WSTG-v42-CLNT-02
OWASP_2021_A04
CWE Id 749
WASC Id
Plugin Id 10110
Low
In Page Banner Information Leak
Description
The server returned a version banner string in the response content. Such information leaks may allow attackers to further target specific issues impacting the product and version in use.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence Tomcat/7.0.70
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence Tomcat/7.0.70
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 2
Solution
Configure the server to prevent such information leaks. For example:

Under Tomcat this is done via the "server" directive and implementation of custom error pages.

Under Apache this is done via the "ServerSignature" and "ServerTokens" directives.
Reference https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/08-Testing_for_Error_Handling/
Tags OWASP_2021_A05
OWASP_2017_A06
WSTG-v42-INFO-02
CWE Id 200
WASC Id 13
Plugin Id 10009
Low
Permissions Policy Header Not Set
Description
Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 9
Solution
Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.
Reference https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
https://developers.google.com/web/updates/2018/06/feature-policy
https://scotthelme.co.uk/a-new-security-header-feature-policy/
https://w3c.github.io/webappsec-feature-policy/
https://www.smashingmagazine.com/2018/12/feature-policy/
Tags OWASP_2021_A01
OWASP_2017_A05
CWE Id 693
WASC Id 15
Plugin Id 10063
Low
Server Leaks Version Information via "Server" HTTP Response Header Field
Description
The web/application server is leaking version information via the "Server" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 285 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence Apache-Coyote/1.1
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 15
Solution
Ensure that your web server, application server, load balancer, etc. is configured to suppress the "Server" header or provide generic details.
Reference http://httpd.apache.org/docs/current/mod/core.html#servertokens
http://msdn.microsoft.com/en-us/library/ff648552.aspx#ht_urlscan_007
http://blogs.msdn.com/b/varunm/archive/2013/04/23/remove-unwanted-http-response-headers.aspx
http://www.troyhunt.com/2012/02/shhh-dont-let-your-response-headers.html
Tags OWASP_2021_A05
OWASP_2017_A06
WSTG-v42-INFO-02
CWE Id 200
WASC Id 13
Plugin Id 10036
Low
X-Content-Type-Options Header Missing
Description
The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
URL http://zero.webappsecurity.com
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 285 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter X-Content-Type-Options
Attack
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
Instances 13
Solution
Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.

If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.
Reference http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspx
https://owasp.org/www-community/Security_Headers
Tags OWASP_2021_A05
OWASP_2017_A06
CWE Id 693
WASC Id 15
Plugin Id 10021
Informational
Base64 Disclosure
Description
Base64 encoded data was disclosed by the application/web server. Note: in the interests of performance not all base64 strings in the response were analyzed individually, the entire response should be looked at by the analyst/security team/developer(s).
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence D27CDB6E-AE6D-11cf-96B8-444553540000
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
Instances 1
Solution
Manually confirm that the Base64 data does not leak sensitive information, and that the data cannot be aggregated/used to exploit other vulnerabilities.
Reference http://projects.webappsec.org/w/page/13246936/Information%20Leakage
Tags OWASP_2021_A04
OWASP_2017_A03
CWE Id 200
WASC Id 13
Plugin Id 10094
Informational
Information Disclosure - Suspicious Comments
Description
The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence query
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence username
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack
Evidence select
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
Instances 3
Solution
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.
Reference
Tags OWASP_2021_A01
OWASP_2017_A03
CWE Id 200
WASC Id 13
Plugin Id 10027
Informational
Modern Web Application
Description
The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence <a id="online-banking" class="btn btn-small btn-info">More Services</a>
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence <a id="online-banking" class="btn btn-small btn-info">More Services</a>
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence <a id="online-banking" class="btn btn-small btn-info">More Services</a>
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence <a href="#"></a>
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence <a href='#'></a>
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
Instances 5
Solution
This is an informational alert and so no changes are required.
Reference
Tags
CWE Id
WASC Id
Plugin Id 10109
Informational
Non-Storable Content
Description
The response contents are not storable by caching components such as proxy servers. If the response does not contain sensitive, personal or user-specific information, it may benefit from being stored and cached, to improve performance.
URL http://zero.webappsecurity.com
Method GET
Parameter
Attack
Evidence no-store
Request Header - size: 213 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/
Method GET
Parameter
Attack
Evidence no-store
Request Header - size: 214 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/index.html
Method GET
Parameter
Attack
Evidence no-store
Request Header - size: 265 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 12,471 bytes.
URL http://zero.webappsecurity.com/search.html?searchTerm=ZAP
Method GET
Parameter
Attack
Evidence no-store
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 242 bytes.
Response Body - size: 7,723 bytes.
Instances 4
Solution
The content may be marked as storable by ensuring that the following conditions are satisfied:

The request method must be understood by the cache and defined as being cacheable ("GET", "HEAD", and "POST" are currently defined as cacheable)

The response status code must be understood by the cache (one of the 1XX, 2XX, 3XX, 4XX, or 5XX response classes are generally understood)

The "no-store" cache directive must not appear in the request or response header fields

For caching by "shared" caches such as "proxy" caches, the "private" response directive must not appear in the response

For caching by "shared" caches such as "proxy" caches, the "Authorization" header field must not appear in the request, unless the response explicitly allows it (using one of the "must-revalidate", "public", or "s-maxage" Cache-Control response directives)

In addition to the conditions above, at least one of the following conditions must also be satisfied by the response:

It must contain an "Expires" header field

It must contain a "max-age" response directive

For "shared" caches such as "proxy" caches, it must contain a "s-maxage" response directive

It must contain a "Cache Control Extension" that allows it to be cached

It must have a status code that is defined as cacheable by default (200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501).
Reference https://tools.ietf.org/html/rfc7234
https://tools.ietf.org/html/rfc7231
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html (obsoleted by rfc7234)
Tags WSTG-v42-ATHN-06
CWE Id 524
WASC Id 13
Plugin Id 10049
Informational
Storable and Cacheable Content
Description
The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.
URL http://zero.webappsecurity.com/resources/css/bootstrap.min.css
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 286 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 115,795 bytes.
URL http://zero.webappsecurity.com/resources/css/font-awesome.css
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 285 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 21,752 bytes.
URL http://zero.webappsecurity.com/resources/css/main.css
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 347 bytes.
Response Body - size: 15,037 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_1.jpg
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 349 bytes.
Response Body - size: 78,506 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_2.jpg
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 112,646 bytes.
URL http://zero.webappsecurity.com/resources/img/main_carousel_3.jpg
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 351 bytes.
Response Body - size: 101,493 bytes.
URL http://zero.webappsecurity.com/resources/js/bootstrap.min.js
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 284 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 26,898 bytes.
URL http://zero.webappsecurity.com/resources/js/jquery-1.8.2.min.js
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 361 bytes.
Response Body - size: 93,436 bytes.
URL http://zero.webappsecurity.com/resources/js/placeholders.min.js
Method GET
Parameter
Attack
Evidence max-age=2678400
Request Header - size: 287 bytes.
Request Body - size: 0 bytes.
Response Header - size: 359 bytes.
Response Body - size: 5,615 bytes.
URL http://zero.webappsecurity.com/robots.txt
Method GET
Parameter
Attack
Evidence
Request Header - size: 224 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 971 bytes.
URL http://zero.webappsecurity.com/sitemap.xml
Method GET
Parameter
Attack
Evidence
Request Header - size: 225 bytes.
Request Body - size: 0 bytes.
Response Header - size: 204 bytes.
Response Body - size: 973 bytes.
Instances 11
Solution
Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:

Cache-Control: no-cache, no-store, must-revalidate, private

Pragma: no-cache

Expires: 0

This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.
Reference https://tools.ietf.org/html/rfc7234
https://tools.ietf.org/html/rfc7231
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html (obsoleted by rfc7234)
Tags WSTG-v42-ATHN-06
CWE Id 524
WASC Id 13
Plugin Id 10049
Informational
User Agent Fuzzer
Description
Check for differences in response based on fuzzed User Agent (eg. mobile sites, access as a Search Engine Crawler). Compares the response statuscode and the hashcode of the response body with the original response.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Evidence
Request Header - size: 255 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Evidence
Request Header - size: 255 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)
Evidence
Request Header - size: 255 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Evidence
Request Header - size: 277 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Evidence
Request Header - size: 288 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16
Evidence
Request Header - size: 346 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources
Method GET
Parameter Header User-Agent
Attack msnbot/1.1 (+http://search.msn.com/msnbot.htm)
Evidence
Request Header - size: 251 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Evidence
Request Header - size: 292 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16
Evidence
Request Header - size: 350 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/css
Method GET
Parameter Header User-Agent
Attack msnbot/1.1 (+http://search.msn.com/msnbot.htm)
Evidence
Request Header - size: 255 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)
Evidence
Request Header - size: 259 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Evidence
Request Header - size: 281 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Evidence
Request Header - size: 292 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16
Evidence
Request Header - size: 350 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/img
Method GET
Parameter Header User-Agent
Attack msnbot/1.1 (+http://search.msn.com/msnbot.htm)
Evidence
Request Header - size: 255 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Evidence
Request Header - size: 258 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Evidence
Request Header - size: 258 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)
Evidence
Request Header - size: 258 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Evidence
Request Header - size: 280 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Evidence
Request Header - size: 291 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16
Evidence
Request Header - size: 349 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
URL http://zero.webappsecurity.com/resources/js
Method GET
Parameter Header User-Agent
Attack msnbot/1.1 (+http://search.msn.com/msnbot.htm)
Evidence
Request Header - size: 254 bytes.
Request Body - size: 0 bytes.
Response Header - size: 267 bytes.
Response Body - size: 949 bytes.
Instances 28
Solution
Reference https://owasp.org/wstg
Tags
CWE Id
WASC Id
Plugin Id 10104